Data clean rooms using defined access with homomorphic encryption

ABSTRACT

A data platform creates an application in a data-provider account, where the application includes one or more application programming interfaces (APIs) corresponding to one or more underlying code blocks. The data platform shares homomorphically encrypted provider data with the application in the data-provider account. The data platform installs, in a data-consumer account, an application instance of the application. The data platform shares homomorphically encrypted consumer data with the application instance in the data-consumer account. The data platform invokes one or more of the APIs of the application instance to execute respective associated underlying code blocks, which are not visible to the data-consumer account, and which operate on the shared homomorphically encrypted provider data and the shared homomorphically encrypted consumer data. The data platform saves homomorphically encrypted output of the one or more respective associated underlying code blocks locally within the data-consumer account.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.18/060,504, filed Nov. 30, 2022 and entitled “Data Clean Rooms UsingDefined Access In Trusted Execution Environment,” which is acontinuation-in-part of U.S. patent application Ser. No. 18/051,457,filed Oct. 31, 2022 and entitled “Data Clean Rooms Using DefinedAccess,” which claims the benefit of U.S. Provisional Patent ApplicationNo. 63/366,316, filed Jun. 13, 2022 and entitled “Data. Clean RoomsUsing Defined Access,” each of which are hereby incorporated byreference into the present disclosure in their respective entireties.

TECHNICAL FIELD

Among other technical fields, embodiments of the present disclosurepertain to managing access to shared data.

BACKGROUND

Data platforms are widely used for data storage and data access incomputing and communication contexts. With respect to architecture, adata platform could be an on-premises data platform, a network-baseddata platform (e.g., a cloud-based data platform), a combination of thetwo, and/or include another type of architecture. With respect to typeof data processing, a data platform could implement online transactionalprocessing (OLTP), online analytical processing (OLAP), a combination ofthe two, and/or another type of data processing. Moreover, a dataplatform could be or include a relational database management system(RDBMS) and/or one or more other types of database management systems.

In a typical implementation, a data platform includes one or moredatabases that are maintained on behalf of a customer account. Indeed, adata platform may include one or more databases that are respectivelymaintained in association with any number of customer accounts. It mayoccur from time to time that users associated with two differentcustomer accounts wish to share data with one another. It can bechallenging, however, to do so in a secure and scalable manner.

A given data platform may also include one or more databases that aremaintained in connection with one or more system (e.g., administrative)accounts of the data platform, one or more other databases used foradministrative purposes, and/or one or more other databases that aremaintained in association with one or more other organizations and/orfor any other purposes. A data platform may store metadata inassociation with the data platform in general and in association withparticular databases and/or particular customer accounts as well.Metadata that is maintained by a data platform with respect to storeddata (e.g., stored customer data) may be referred to herein at times as“expression properties.”

Users and/or executing processes (that may be associated with, e.g., agiven customer account) may, via one or more types of clients, be ableto cause data to be ingested into one or more databases in the dataplatform, and may also be able to manipulate the data, run queriesagainst the data, create customized views (which are also known assecure views) of the data, modify the data, insert additional data,remove data, and/or the like. Some example types of clients include webinterfaces, Java Database Connectivity (JDBC) drivers, Open DatabaseConnectivity (ODBC) drivers, one or more other types of drivers, desktopapplications, mobile apps, and the like.

BRIEF DESCRIPTION OF THE DRAWINGS

A more detailed understanding may be had from the following description,which is presented by way of example in conjunction with the followingdrawings, in which like reference numerals are used across the drawingsin connection with like elements.

FIG. 1 illustrates an example computing environment in which a dataplatform may provide data clean rooms, in accordance with at least oneembodiment.

FIG. 2 is a block diagram illustrating components of a compute servicemanager, in accordance with at least one embodiment.

FIG. 3 is a block diagram illustrating components of an executionplatform, in accordance with at least one embodiment.

FIG. 4 illustrates an example data-provider data table and an exampledata-consumer data table, in accordance with at least one embodiment.

FIG. 5 depicts a first example defined-access data-clean-room scenario,in accordance with at least one embodiment.

FIG. 6 shows a flow diagram of a first method for providing definedaccess in the context of a data clean room, in accordance with at leastone embodiment.

FIG. 7 depicts a second example defined-access data-clean-room scenario,in accordance with at least one embodiment.

FIG. 8 shows a flow diagram of a second method for providing definedaccess in the context of a data clean room, in accordance with at leastone embodiment.

FIG. 9 depicts a third example defined-access data-clean-room scenario,in accordance with at least one embodiment.

FIG. 10 shows a flow diagram of a third method for providing definedaccess in the context of a data clean room, in accordance with at leastone embodiment.

FIG. 11 illustrates a diagrammatic representation of a machine in theform of a computer system within which a set of instructions may beexecuted for causing the machine to perform any one or more of themethodologies discussed herein, in accordance with at least oneembodiment.

DETAILED DESCRIPTION

The description that follows includes systems, methods, techniques,instruction sequences, and computing machine program products thatembody illustrative embodiments of the disclosure. In the followingdescription, for the purposes of explanation, numerous specific detailsare set forth in order to provide an understanding of variousembodiments of the inventive subject matter. It will be evident,however, to those skilled in the art, that embodiments of the inventivesubject matter may be practiced without these specific details. Ingeneral, well-known instruction instances, protocols, structures, andtechniques are not necessarily shown in detail.

Data clean rooms enable two or more parties to share data, whilerestricting how that data can be used by other parties. In one examplescenario, two or more parties wish to combine their respective datawithout revealing their raw data to each other. For example, twocompanies may wish to determine how many joint customers they have, butneither company wants to give the other one access to its customer list.A data clean room can be established for processing a join of a customerlist from one company with a customer list from the other company, usinga field such as mobile phone number or email address as a join key, asan example.

Each company may share its respective customer list with the othercompany via a data clean room, within which the aforementioned join canbe executed, and a total number of rows in the resulting relation can beconveyed back to each party. In that manner, neither company ever hasaccess to the actual customer data on the other's list, but each companycan find out the number of common customers between the two companies.In an example such as this, the data clean room may be resident in adatabase-platform account of either company or in a mutually agreed-uponlocation that is in neither database-platform account, and each companymay confidentially share its customer list (or perhaps just one or morecolumns of its customer list) with the data clean room, within which thejoin function may be carried out.

The above-described example relates in many instances to atwo-way-sharing model i.e., each company shares its customer list withthe other to at least some extent. There are other scenarios, however,in which the data-sharing model is more of a one-way street. Thisdisclosure includes description of example data-clean-room operation insome such example scenarios. In this disclosure, the sharingrelationship is described as being between (i) a company (ororganization or an individual, etc.) that is referred to herein as a“data provider” and (ii) a company (or, again, an organization or anindividual, etc.) that is referred to herein as a “data consumer.” Asone would expect from those names, a given data provider provides datathat is consumed by one or more data consumers. In the examples that areprimarily described below in connection with the figures, the dataprovider is a streaming-video platform that presents advertisements(“ads”) in conjunction with the streaming video that it provides, andthe data consumer is a particular advertiser that advertises on thatstreaming service.

Embodiments of the present disclosure are described herein as using dataclean rooms that are constructed and operated according to what isreferred to herein as “defined access” (or “a defined-access model,” “adefined-access paradigm,” “a defined-access approach,” and/or the like).In at least one embodiment, a data provider creates an application. Insome embodiments, the application may be what is referred to in thepresent disclosure as a “native platform application,” which, as usedherein, refers to an application that is “built in” to i.e., executes onthe herein-described data platform. Generally speaking, any suitabletype of application can be used in a given embodiment of the presentdisclosure; the mention of native platform applications in the previoussentence is by way of example only.

In some of the described examples, both the data providers and the dataconsumers are customers of a common data platform, and accordingly eachhave a respective customer account (or just “account”) on that dataplatform. In other embodiments, a given data provider and a given dataconsumer operate on separate platforms. Either or both of the separateplatforms could be platforms operated by the data provider or dataconsumer themselves, or could be a customer account held by the dataprovider or the data consumer on another multi-customer data platform.And certainly other architectures are possible as well.

In at least one embodiment in which the data provider and the dataconsumer operate their own respective platform, it may be the case thatneither fully trusts the other to fully implement what each party deemsto be the appropriate security measures. In one or more embodiments,both the data provider and the data consumer may place their trust inwhat is known as a trusted execution environment (TEE). An example TEEcould be a secure enclave, a confidential virtual machine (VM), oranother option deemed suitable by those of skill in the art having thebenefit of the present disclosure. These embodiments are referred toherein at times as “TEE embodiments.”

Moreover, in some embodiments in which the data provider and the dataconsumer operate their own respective platform, the data provider andthe data consumer use cryptographic protection of their data in use(e.g., during computations). These embodiments are discussed below inconnection with FIG. 9 and FIG. 10 , and are referred to in the presentdisclosure at times as “cryptography embodiments.” It is noted that thedata provider and the data consumer may also use cryptographicprotection of their data at rest and/or their data in transit. Lastly,embodiments in which both the data provider and the data consumer haveaccounts on a common data platform may be referred to herein at times as“common-platform embodiments.”

In at least one TEE embodiment, an application having one or more APIsas described herein may execute on a given TEE. The data provider mayprovide the application and may share certain of the data provider'sdata with that application. An instance of that application may then beinstalled in the TEE, and the data consumer may share certain of thedata consumer's data with that application instance. In someembodiments, both the data provider and the data consumer share theirrespective data with the installed application instance. Otherarchitectures are possible as well and may occur to those of skill inthe art having the benefit of the present disclosure. Some TEEembodiments are further discussed below in connection with FIG. 7 andFIG. 8 .

In at least one cryptography embodiment, the data provider may providean application having one or more APIs as discussed herein, and mayshare certain of the data provider's data with that application on thedata provider's platform (i.e., “the data-provider platform”). Aninstance of that application may be installed on the data consumer'splatform (i.e., “the data-consumer platform”), and the data consumer mayshare certain of the data consumer's data with that applicationinstance.

In some cryptography embodiments, the installed application instance mayimplement what is known in the art as fully homomorphic encryption (FHE)(or another type of homomorphic encryption). In such embodiments, boththe data-provider data and the data-consumer data that are shared withthe application instance may be homomorphically encrypted, and the oneor more APIs of the installed application instance may operate on thishomomorphically encrypted data, and return a homomorphically encryptedresult to the data consumer for local decryption and storage on thedata-consumer platform. In at least some such embodiments, both the dataprovider and the data consumer may homomorphically encrypt theirrespective data using a public key generated by the data consumer. Thedata consumer may share that public key with the data provider, thoughonly the data consumer has the corresponding secret key needed todecrypt the results. Other encryption-based approaches can be used aswell. Moreover, FHE can be used in multiple types of embodiments,including common-platform embodiments, TEE embodiments, and embodimentsin which the data provider and the data consumer operate their ownrespective platform, as examples.

Returning for now to discussion of some example common-platformembodiments, a given application may reside in the data-platform accountof a data provider (the “data-provider account”), and may include a setof application programming interfaces (APIs) that are associated withvarious underlying blocks of (e.g., source and/or executable) codeprovided by the given application. In at least some embodiments, theseAPIs define how data in the data-provider account (“provider data”) maybe accessed by any user that is executing an instance of the givenapplication. The underlying code blocks may perform operations thatinclude, but are not limited to, particular queries, particular queryoperations (e.g., joins), user-defined functions, other functions,stored procedures, scripts, user-interface elements, secure views,and/or the like. The data provider may share certain data with theapplication.

The data provider may further permit a data consumer to install aninstance of the application. It is noted that there may be multiple dataproviders, multiple applications provided by a given data provider,multiple data consumers, multiple application instances installed by agiven data consumer, and so forth. For simplicity, however, most of theexamples that are described in the present disclosure involve a singledata provider that has created a single application in the data-provideraccount of that data provider, and a single data consumer that installsa single instance of that application in the data-consumer account ofthat data consumer.

Once the data consumer has installed, in the data-consumer account, aninstance of the application, the data consumer can thereafter use theone or more APIs provided by the data provider to access the providerdata (to the extent permitted by the code underlying the APIs). Becausethe APIs are created by (or at least for) the provider, the APIs enforcethe provider's intended restrictions on how provider data may be used.In at least one embodiment, the APIs themselves are visible to thedata-consumer account, whereas the operational logic (e.g., source code,executable code, and/or the like) of the underlying code blocks is not.In at least some embodiments, the provider data is homomorphicallyencrypted, and the code underlying the APIs operates on that encrypteddata.

In many examples, data consumers combine at least some of their ownconsumer data with the accessed provider data via the APIs, Thus, insome embodiments, the data provider shares certain provider data withthe application, and also shares the application with the data consumer,whereas the data consumer shares at least some of its consumer data withthe installed application instance. This arrangement protects the dataof both parties, and in particular protects the consumer data, which isonly being shared within the data-consumer account with the particularinstalled instance of the described application. Indeed, in at least oneembodiment, the application is constructed such that it is not able toexfiltrate consumer data from the data-consumer account (absentauthorization from the data consumer).

Moreover, in at least one embodiment, results computed by (or generatedby, etc.) a given API are returned only locally within the data-consumeraccount within which that particular application instance has beeninstalled and is executing. Furthermore, in at least one embodiment, thedata consumer is protected in that both the provider data and theconsumer data are homomorphically encrypted using a public key generatedby the data consumer. The provider data and consumer data are operatedon while encrypted, and the results are not only returned exclusively tothe data consumer, but those results are also homomorphically encryptedwith the data consumer's public key, where only the data consumerpossesses the corresponding secret key needed to decrypt the results.

It is noted that, as used herein, “share” (or “sharing,” etc.) is abroad verb that is intended to include mechanisms such as grantingpermissions, sending copies, sending links (e.g., customized links),and/or any other mechanism by which access to the party being sharedwith can be accomplished. In some cases, “sharing” involves grantingpermissions to one or more objects that may represent, e.g., a database,an application, an application instance, and/or the like.

Additionally, in at least one embodiment, data providers are equippedwith one or more tools or other mechanisms that can be used to audit howone or more data consumers are accessing the provider data of that dataprovider. Some examples of auditable events include API invocations,stored-procedure invocations, accesses of certain tables, accesses ofcertain views, accesses of certain databases, accesses of certainobjects, and/or the like. In some embodiments, data providers have thecapability to revoke granted access (e.g., at will, or under certainconditions, etc.).

In some embodiments, an audit log (or other record) is generated torecord various events. Such an audit log may include details of how thedata provider's data was used—e.g., whether a particular column was usedas a join key or filter, or directly returned to the data consumer,among other options. An audit log may include computation details,totals, and/or the like. For example, an audit log may include a valuesuch as volume of data produced. Moreover, in embodiments in which adata consumer's query involves the data consumer's own data in additionto the data provider's data, an audit function may record only metricsand events related to the data consumer's access of the data provider'sdata, but not record metrics and events regarding how the data consumermay or may not have accessed their own data. This may protect privacyand confidentiality of the data consumer's data. Numerous otherpossibilities could be implemented as well or instead of one or more ofthe aforementioned options.

FIG. 1 illustrates an example computing environment 100 that includes adatabase system in the example form of a data platform 102, inaccordance with some embodiments of the present disclosure. To avoidobscuring the inventive subject matter with unnecessary detail, variousfunctional components that are not germane to conveying an understandingof the inventive subject matter have been omitted from FIG. 1 . However,a skilled artisan will readily recognize that various additionalfunctional components may be included as part of the computingenvironment 100 to facilitate additional functionality that is notspecifically described herein. In other embodiments, the computingenvironment may comprise another type of network-based database systemor a cloud data platform.

As shown, the computing environment 100 comprises the data platform 102in communication with a cloud storage platform 104 (e.g., AWS®,Microsoft Azure Blob Storage®, or Google Cloud Storage). The dataplatform 102 is a network-based system used for reporting and analysisof integrated data from one or more disparate sources including one ormore storage locations within the cloud storage platform 104. The cloudstorage platform 104 comprises a plurality of computing machines andprovides on-demand computer system resources such as data storage andcomputing power to the data platform 102.

The data platform 102 comprises a compute service manager 108, anexecution platform 110, and one or more metadata databases 112. The dataplatform 102 hosts and provides data reporting and analysis services tomultiple client accounts.

The compute service manager 108 coordinates and manages operations ofthe data platform 102. The compute service manager 108 also performsquery optimization and compilation as well as managing clusters ofcomputing services that provide compute resources (also referred to as“virtual warehouses”), The compute service manager 108 can support anynumber of client accounts, such as end users providing data storage andretrieval requests, system administrators managing the systems andmethods described herein, and other components/devices that interactwith compute service manager 108.

The compute service manager 108 is also in communication with a clientdevice 114. The client device 114 corresponds to a user of one of themultiple client accounts supported by the data platform 102, A user mayutilize the client device 114 to submit data storage, retrieval, andanalysis requests to the compute service manager 108.

The compute service manager 108 is also coupled to one or more metadatadatabases 112 that store metadata pertaining to various functions andaspects associated with the data platform 102 and its users. Forexample, metadata database(s) 112 may include a summary of data storedin remote data storage systems as well as data available from a localcache. Additionally, metadata database(s) 112 may include informationregarding how data is partitioned and organized in remote data storagesystems (e.g., the cloud storage platform 104) and local caches.

As discussed herein, a “micro-partition” is a batch storage unit, andeach micro-partition has contiguous units of storage. By way of example,each micro-partition may contain between 50 MB and 500 MB ofuncompressed data (note that the actual size in storage may be smallerbecause data may be stored compressed). Groups of rows in tables may bemapped into individual micro-partitions organized in a columnar fashion.This size and structure allows for extremely granular selection of themicro-partitions to be scanned, which can include millions, or evenhundreds of millions, of micro-partitions. This granular selectionprocess for micro-partitions to be scanned is referred to herein as“pruning.” Pruning involves using metadata to determine which portionsof a table, including which micro-partitions or micro-partitiongroupings in the table, are not pertinent to a query, avoiding thosenon-pertinent micro-partitions when responding to the query, andscanning only the pertinent micro-partitions to respond to the query.

Metadata may be automatically gathered on all rows stored in amicro-partition, including: the range of values for each of the columnsin the micro-partition; the number of distinct values; and/or additionalproperties used for both optimization and efficient query processing. Inone embodiment; micro-partitioning may be automatically performed on alltables. For example, tables may be transparently partitioned using theordering that occurs when the data is inserted/loaded. However, itshould be appreciated that this disclosure of the micro-partition isexemplary only and should be considered non-limiting. It should beappreciated that the micro-partition may include other database storagedevices without departing from the scope of the disclosure. Informationstored by a metadata database 112 (e.g., key-value pair data store)allows systems and services to determine whether a piece of data (e.g.,a given partition) needs to be accessed without loading or accessing theactual data from a storage device.

The compute service manager 108 is further coupled to the executionplatform 110, which provides multiple computing resources that executevarious data storage and data retrieval tasks. The execution platform110 is coupled to cloud storage platform 104. The cloud storage platform104 comprises multiple data storage devices 120-1 to 120-N. In someembodiments, the data storage devices 120-1 to 120-N are cloud-basedstorage devices located in one or more geographic locations. Forexample, the data storage devices 120-1 to 120-N may be part of a publiccloud infrastructure or a private cloud infrastructure. The data storagedevices 120-1 to 120-N may be hard disk drives (HDDs), solid statedrives (SSDs), storage clusters, Amazon S3TM storage systems, or anyother data storage technology. Additionally, the cloud storage platform104 may include distributed file systems (such as Hadoop DistributedFile Systems (HDFS)), object storage systems, and the like.

The execution platform 110 comprises a plurality of compute nodes. A setof processes on a compute node executes a query plan compiled by thecompute service manager 108, The set of processes can include: a firstprocess to execute the query plan; a second process to monitor anddelete cache files using a least recently used (LRU) policy andimplement an out-of-memory (OOM) error mitigation process; a thirdprocess that extracts health information from process logs and status tosend back to the compute service manager 108; a fourth process toestablish communication with the compute service manager 108 after asystem boot; and a fifth process to handle all communication with acompute cluster for a given job provided by the compute service manager108 and to communicate information back to the compute service manager108 and other compute nodes of the execution platform 110.

In some embodiments, communication links between elements of thecomputing environment 100 are implemented via one or more datacommunication networks. These data communication networks may utilizeany communication protocol and any type of communication medium. In someembodiments, the data communication networks are a combination of two ormore data communication networks (or sub-networks) coupled to oneanother. In alternative embodiments; these communication links areimplemented using any type of communication medium and any communicationprotocol.

The compute service manager 108, metadata database(s) 112, executionplatform 110, and cloud storage platform 104 are shown in FIG. 1 asindividual discrete components. However, each of the compute servicemanagers 108, metadata databases 112; execution platforms 110; and cloudstorage platforms 104 may be implemented as a distributed system (e.g.,distributed across multiple systems/platforms at multiple geographiclocations), Additionally, each of the compute service managers 108;metadata databases 112; execution platforms 110; and cloud storageplatforms 104 can be scaled up or down (independently of one another)depending on changes to the requests received and the changing needs ofthe data platform 102, Thus, in the described embodiments, the dataplatform 102 is dynamic and supports regular changes to meet the currentdata processing needs.

During typical operation, the data platform 102 processes multiple jobsdetermined by the compute service manager 108. These jobs are scheduledand managed by the compute service manager 108 to determine when and howto execute the job. For example, the compute service manager 108 maydivide the job into multiple discrete tasks and may determine what datais needed to execute each of the multiple discrete tasks. The computeservice manager 108 may assign each of the multiple discrete tasks toone or more nodes of the execution platform 110 to process the task. Thecompute service manager 108 may determine what data is needed to processa task and further determine which nodes within the execution platform110 are best suited to process the task. Some nodes may have alreadycached the data needed to process the task and, therefore, be a goodcandidate for processing the task.

Metadata stored in a metadata database 112 assists the compute servicemanager 108 in determining which nodes in the execution platform 110have already cached at least a portion of the data needed to process thetask. One or more nodes in the execution platform 110 process the taskusing data cached by the nodes and, if necessary, data retrieved fromthe cloud storage platform 104. It is desirable to retrieve as much dataas possible from caches within the execution platform 110 because theretrieval speed is typically much faster than retrieving data from thecloud storage platform 104.

As shown in FIG. 1 , the computing environment 100 separates theexecution platform 110 from the cloud storage platform 104. In thisarrangement, the processing resources and cache resources in theexecution platform 110 operate independently of the data storage devices120-1 to 120-N in the cloud storage platform 104. Thus, the computingresources and cache resources are not restricted to specific datastorage devices 120-1 to 120-N. Instead, all computing resources and allcache resources may retrieve data from, and store data to, any of thedata storage resources in the cloud storage platform 104.

FIG. 2 is a block diagram illustrating components of the compute servicemanager 108, in accordance with some embodiments of the presentdisclosure. As shown in FIG. 2 , the compute service manager 108includes an access manager 202 and a credential management system 204coupled to access metadata database 206, which is an example of themetadata databases 112. Access manager 202 handles authentication andauthorization tasks for the systems described herein. The credentialmanagement system 204 facilitates use of remote stored credentials toaccess external resources such as data resources in a remote storagedevice. As used herein, the remote storage devices may also be referredto as “persistent storage devices” or “shared storage devices.” Forexample, the credential management system 204 may create and maintainremote credential store definitions and credential objects (e.g., in theaccess metadata database 206), A remote credential store definitionidentifies a remote credential store and includes access information toaccess security credentials from the remote credential store, Acredential object identifies one or more security credentials usingnon-sensitive information (e.g., text strings) that are to be retrievedfrom a remote credential store for use in accessing an externalresource. When a request invoking an external resource is received atrun time, the credential management system 204 and access manager 202use information stored in the access metadata database 206 (e.g., acredential object and a credential store definition) to retrievesecurity credentials used to access the external resource from a remotecredential store.

A request processing service 208 manages received data storage requestsand data retrieval requests (e.g., jobs to be performed on databasedata), For example, the request processing service 208 may determine thedata to process a received query (e.g., a data storage request or dataretrieval request). The data may be stored in a cache within theexecution platform 110 or in a data storage device in cloud storageplatform 104.

A management console service 210 supports access to various systems andprocesses by administrators and other system managers. Additionally, themanagement console service 210 may receive a request to execute a joband monitor the workload on the system.

The compute service manager 108 also includes a job compiler 212, a joboptimizer 214, and a job executor 216. The job compiler 212 parses a jobinto multiple discrete tasks and generates the execution code for eachof the multiple discrete tasks. The job optimizer 214 determines thebest method to execute the multiple discrete tasks based on the datathat needs to be processed. The job optimizer 214 also handles variousdata pruning operations and other data optimization techniques toimprove the speed and efficiency of executing the job. The job executor216 executes the execution code for jobs received from a queue ordetermined by the compute service manager 108.

A job scheduler and coordinator 218 sends received jobs to theappropriate services or systems for compilation, optimization, anddispatch to the execution platform 110 of FIG. 1 . For example, jobs maybe prioritized and then processed in that prioritized order. In anembodiment, the job scheduler and coordinator 218 determines a priorityfor internal jobs that are scheduled by the compute service manager 108of FIG. 1 with other “outside” jobs such as user queries that may bescheduled by other systems in the database but may utilize the sameprocessing resources in the execution platform 110, In some embodiments,the job scheduler and coordinator 218 identifies or assigns particularnodes in the execution platform 110 to process particular tasks, Avirtual warehouse manager 220 manages the operation of multiple virtualwarehouses implemented in the execution platform 110. For example, thevirtual warehouse manager 220 may generate query plans for executingreceived queries. The data clean room system 230 is configured toperform online error checking and offline error checking, as discussedin further detail below, and is further configured to conduct thedata-clean-room-related functions described in the present disclosure.

As illustrated, the compute service manager 108 includes a configurationand metadata manager 222, which manages the information related to thedata stored in the remote data storage devices and in the local buffers(e.g., the buffers in execution platform 110). The configuration andmetadata manager 222 uses metadata to determine which data files need tobe accessed to retrieve data for processing a particular task or job, Amonitor and workload analyzer 224 oversees processes performed by thecompute service manager 108 and manages the distribution of tasks (e.g.,workload) across the virtual warehouses and execution nodes in theexecution platform 110. The monitor and workload analyzer 224 alsoredistributes tasks, as needed, based on changing workloads throughoutthe data platform 102 and may further redistribute tasks based on a user(e.g., “external”) query workload that may also be processed by theexecution platform 110. The configuration and metadata manager 222 andthe monitor and workload analyzer 224 are coupled to a data storagedevice 226. Data storage device 226 represents any data storage devicewithin the data platform 102. For example, data storage device 226 mayrepresent buffers in execution platform 110, storage devices in cloudstorage platform 104, or any other storage device.

As described in embodiments herein, the compute service manager 108validates all communication from an execution platform (e.g., theexecution platform 110) to validate that the content and context of thatcommunication are consistent with the task(s) known to be assigned tothe execution platform. For example, an instance of the executionplatform executing a query A should not be allowed to request access todata-source D (e.g., data storage device 226) that is not relevant toquery A. Similarly, a given execution node (e.g., execution node 302-1of FIG. 3 ) may need to communicate with another execution node (e.g.,execution node 302-2 of FIG. 3 ), but should be disallowed fromcommunicating with a third execution node (e.g., execution node 312-1),and any such illicit communication can be recorded (e.g., in a log orother location). Also, the information stored on a given execution nodeis restricted to data relevant to the current query, and any other datais unusable, rendered so by destruction or encryption where the key isunavailable.

FIG. 3 is a block diagram illustrating components of the executionplatform 110 of FIG. 1 , in accordance with some embodiments. As shownin FIG. 3 , the execution platform 110 includes multiple virtualwarehouses, including virtual warehouse 1, virtual warehouse 2, andvirtual warehouse N. Each virtual warehouse includes multiple executionnodes that each include a data cache and a processor. The virtualwarehouses can execute multiple tasks in parallel by using the multipleexecution nodes.

As discussed herein, the execution platform 110 can add new virtualwarehouses and drop existing virtual warehouses in real-time based onthe current processing needs of the systems and users. This flexibilityallows the execution platform 110 to quickly deploy large amounts ofcomputing resources when needed without being forced to continue payingfor those computing resources when they are no longer needed. Allvirtual warehouses can access data from any data storage device (e.g.,any storage device in cloud storage platform 104).

Although each virtual warehouse shown in FIG. 3 includes three executionnodes, a particular virtual warehouse may include any number ofexecution nodes. Further, the number of execution nodes in a virtualwarehouse is dynamic, such that new execution nodes are created whenadditional demand is present, and existing execution nodes are deletedwhen they are no longer useful.

Each virtual warehouse is capable of accessing any of the data storagedevices 120-1 to 120-N shown in FIG. 1 . Thus, the virtual warehousesare not necessarily assigned to a specific data storage device 120-1 to120-N and, instead, can access data from any of the data storage devices120-1 to 120-N within the cloud storage platform 104, Similarly, each ofthe execution nodes shown in FIG. 3 can access data from any of the datastorage devices 120-1 to 120-N. In some embodiments, a particularvirtual warehouse or a particular execution node may be temporarilyassigned to a specific data storage device, but the virtual warehouse orexecution node may later access data from any other data storage device.

In the example of FIG. 3 , virtual warehouse 1 includes three executionnodes 302-1, 302-2, and 302-N. Execution node 302-1 includes a cache304-1 and a processor 306-1, Execution node 302-2 includes a cache 304-2and a processor 306-2. Execution node 302-N includes a cache 304-N and aprocessor 306-N. Each execution node 302-1, 302-2, and 302-N isassociated with processing one or more data storage and/or dataretrieval tasks. For example, a virtual warehouse may handle datastorage and data retrieval tasks associated with an internal service,such as a clustering service, a materialized view refresh service, afile compaction service, a storage procedure service, or a file upgradeservice. In other implementations, a particular virtual warehouse mayhandle data storage and data retrieval tasks associated with aparticular data storage system or a particular category of data.

Similar to virtual warehouse 1 discussed above, virtual warehouse 2includes three execution nodes 312-1, 312-2, and 312-N. Execution node312-1 includes a cache 314-1 and a processor 316-1. Execution node 312-2includes a cache 314-2 and a processor 316-2. Execution node 312-Nincludes a cache 314-N and a processor 316-N. Additionally, virtualwarehouse 3 includes three execution nodes 322-1, 322-2, and 322-N.Execution node 322-1 includes a cache 324-1 and a processor 326-1.Execution node 322-2 includes a cache 324-2 and a processor 326-2.Execution node 322-N includes a cache 324-N and a processor 326-N.

In some embodiments, the execution nodes shown in FIG. 3 are statelesswith respect to the data being cached by the execution nodes. Forexample, these execution nodes do not store or otherwise maintain stateinformation about the execution node or the data being cached by aparticular execution node. Thus, in the event of an execution nodefailure, the failed node can be transparently replaced by another node,Since there is no state information associated with the failed executionnode, the new (replacement) execution node can easily replace the failednode without concern for recreating a particular state.

Although the execution nodes shown in FIG. 3 each include one data cacheand one processor, alternative embodiments may include execution nodescontaining any number of processors and any number of caches.Additionally, the caches may vary in size among the different executionnodes. The caches shown in FIG. 3 store, in the local execution node,data that was retrieved from one or more data storage devices in cloudstorage platform 104 of FIG. 1 . Thus, the caches reduce or eliminatethe bottleneck problems occurring in platforms that consistentlyretrieve data from remote storage systems. Instead of repeatedlyaccessing data from the remote storage devices, the systems and methodsdescribed herein access data from the caches in the execution nodes,which is significantly faster and avoids the bottleneck problemdiscussed above. In some embodiments, the caches are implemented usinghigh-speed memory devices that provide fast access to the cached data.Each cache can store data from any of the storage devices in the cloudstorage platform 104.

Further, the cache resources and computing resources may vary betweendifferent execution nodes. For example, one execution node may containsignificant computing resources and minimal cache resources, making theexecution node useful for tasks that require significant computingresources. Another execution node may contain significant cacheresources and minimal computing resources, making this execution nodeuseful for tasks that require caching of large amounts of data. Yet,another execution node may contain cache resources providing fasterinput-output operations, useful for tasks that require fast scanning oflarge amounts of data. In some embodiments, the cache resources andcomputing resources associated with a particular execution node aredetermined when the execution node is created, based on the expectedtasks to be performed by the execution node.

Additionally, the cache resources and computing resources associatedwith a particular execution node may change over time based on changingtasks performed by the execution node. For example, an execution nodemay be assigned more processing resources if the tasks performed by theexecution node become more processor-intensive. Similarly, an executionnode may be assigned more cache resources if the tasks performed by theexecution node require a larger cache capacity.

Although virtual warehouses 1, 2, and N are associated with the sameexecution platform 110, the virtual warehouses may be implemented usingmultiple computing systems at multiple geographic locations. Forexample, virtual warehouse 1 can be implemented by a computing system ata first geographic location, while virtual warehouses 2 and N areimplemented by another computing system at a second geographic location.In some embodiments, these different computing systems are cloud-basedcomputing systems maintained by one or more different entities.

Additionally, each virtual warehouse is shown in 3 as having multipleexecution nodes. The multiple execution nodes associated with eachvirtual warehouse may be implemented using multiple computing systems atmultiple geographic locations. For example, an instance of virtualwarehouse 1 implements execution nodes 302-1 and 302-2 on one computingplatform at a geographic location and implements execution node 302-N ata different computing platform at another geographic location. Selectingparticular computing systems to implement an execution node may dependon various factors, such as the level of resources needed for aparticular execution node (e.g., processing resource requirements andcache requirements), the resources available at particular computingsystems, communication capabilities of networks within a geographiclocation or between geographic locations, and which computing systemsare already implementing other execution nodes in the virtual warehouse.

Execution platform 110 is also fault tolerant. For example, if onevirtual warehouse fails, that virtual warehouse is quickly replaced witha different virtual warehouse at a different geographic location.

A particular execution platform 110 may include any number of virtualwarehouses. Additionally, the number of virtual warehouses in aparticular execution platform is dynamic, such that new virtualwarehouses are created when additional processing and/or cachingresources are needed. Similarly, existing virtual warehouses may bedeleted when the resources associated with the virtual warehouse are nolonger useful.

In some embodiments, the virtual warehouses may operate on the same datain cloud storage platform 104, but each virtual warehouse has its ownexecution nodes with independent processing and caching resources. Thisconfiguration allows requests on different virtual warehouses to beprocessed independently and with no interference between the requests.This independent processing, combined with the ability to dynamicallyadd and remove virtual warehouses, supports the addition of newprocessing capacity for new users without impacting the performance.

Further examples of embodiments are described below in connection withFIG. 4 through FIG. 10 . In the first example scenario described below,a data provider and a data consumer are both customers of the dataplatform 102, and each has a respective account (e.g., customer account)with the data platform 102. These customer accounts may be maintained bythe data platform 102 in the cloud storage platform 104. The exampledata provider is a streaming-video platform that presents advertisementsin connection with presented video. The example data consumer is oneparticular advertiser that places ads on the streaming-video platform.

FIG. 4 illustrates an example data-provider data table 400 and anexample data-consumer data table 450, in accordance with at least oneembodiment. The data-provider data table 400 may be stored in thedata-provider account, whereas the data-consumer data table 450 may bestored in the data-consumer account. The data content and arrangementspresented in FIG. 4 are by way of example and not limitation, as othercontent and/or arrangements could be used.

The data-provider data table 400 has a header row and a row for each ofa plurality of customers, and further has columns correspondingrespectively to a customer ID and an email address. The data-providerdata table 400 also includes columns for an arbitrary number M ofadvertisements. For each customer, an indication of ‘true’ or ‘false’indicates whether or not the customer of that row has viewed (or hasbeen presented, etc.) the ad of that column. Respective rows for anarbitrary number N of customers is shown in the data-provider data table400.

The data-consumer data table 450 has a header row and a row for each ofan arbitrary number K of customers of the data consumer, as well ascolumns corresponding to a customer ID and an email address. Thedata-consumer data table 450 further includes an arbitrary number L ofcolumns that respectively contain ‘true’ or ‘false’ to indicate whetheror not the customer of that row has purchased the product of thatcolumn. For simplicity, ‘AD01’ is an advertisement for ‘PRODUCT01,’ and‘AD02’ is an advertisement for ‘PRODUCT02.’ The names PRODUCT01 andPRODUCT02 are simply placeholders, and could just as well represent agiven service, a collection of products, and/or the like.

It can be seen from inspection of the data-provider data table 400 andthe data-consumer data table 450 that there are four common customersbetween the two tables. In particular, customers 1-4 in thedata-provider data table 400 correspond respectively to customers 46,47, 49, and 50 in the data-consumer data table 450, The rows in thedata-consumer data table 450 that correspond to those four examplecustomers are marked with an arrow to the left of each such row.Moreover, it is noted that, in some embodiments, customers will onlyappear in a given table if they viewed a given ad or bought a givenproduct thus, more of a transaction-log approach is used in someembodiments. Other approaches could be used as well, and may occur tothose of skill in the art having the benefit of the present disclosure.

FIG. 5 depicts an example defined-access data-clean-room scenario 500,in accordance with at least one embodiment. Depicted in FIG. 5 arerepresentations of (i) a data-provider account 502 corresponding withthe above-described streaming-video platform and (ii) a data-consumeraccount 552 corresponding with the above-described advertiser. Thedata-provider account 502 includes provider data 504 and an application506. The provider data 504 may include the data-provider data table 400of FIG. 4 . Furthermore, a share 512 is depicted to represent that atleast some of the provider data 504 is shared with the application 506,In this example, the shared data is the data-provider data table 400.

Furthermore, the application 506 includes one or more APIs 508 thatcorrespond with one or more respective underlying code blocks 510. TheseAPIs 508 and associated underlying code blocks 510 could provide any ofthe operations described above, including queries, query operations(e.g., joins), user-defined functions, stored procedures, access to oneor more secure views, generation of one or more user-interface elements,and/or the like. In at least one embodiment, the underlying code blocks510 contain the source code and/or executable code that actuallyperforms the operations that are accessible via the APIs 508.

A share 520 depicts that the data-provider account 502 is sharing theapplication 506 with the data-consumer account 552. In at least oneembodiment, this involves permitting the installation in thedata-consumer account 552 of an application instance 556 of theapplication 506. As can be seen in FIG. 5 , the application instance 556includes one or more APIs 558 that correspond to the one or more APIs508 of the application 506. The APIs 558 respectively provide access toone or more underlying code blocks 560, which correspond to the one ormore underlying code blocks 510 in the application 506. Whereas theunderlying code blocks 510 (e.g., the underlying source code and/orexecutable code) are visible to the data-provider account 502, theunderlying code blocks 560 are not visible to the data-consumer account552—for this reason, the underlying code blocks 560 are depicted usingdashed outlines in FIG. 5 .

It can further be seen that the data-consumer account 552 containsconsumer data 554 which, in this example, includes the above-describeddata-consumer data table 450 of FIG. 4 . The share 562 that is depictedin FIG. 5 represents that the data-consumer account 552 is sharing atleast some of the consumer data 554 with the application instance 556.It is noted with respect to both the provider data 504 and the consumerdata 554 that their depiction as being respectively within thedata-provider account 502 and the data-consumer account 552 areillustrative only, and do not necessarily reflect an actual storagelocation.

When the data-consumer account 552 uses one or more of the APIs 558 ofthe application instance 556, any output of these operations is depictedas being stored in the consumer data 554 of the data-consumer account552. The security of the consumer data 554 is protected in at least twoways: it never leaves the data-consumer account 552, and even theresulting output 570 is locally stored in the data-consumer account 552.Furthermore, as described herein, the provider data 504, the consumerdata 554, and the output 570 (i.e., results) may also be protected usinghomomorphic encryption.

FIG. 6 shows a flow diagram of a method 600 for providing defined accessin the context of a data clean room, in accordance with at least oneembodiment. The example method 600 is described by way of example asbeing performed by the data platform 102, though this is by way ofexample and not limitation. The method 600 could be performed by any oneor more computing devices that are suitably, programmed to perform thedescribed functions.

At operation 602, the data platform 102 creates the application 506 inthe data-provider account 502 of the data platform 102. The application506 includes the one or more APIs 508 corresponding to the one or moreunderlying code blocks 510.

At operation 604, the data platform 102 shares (at the share 512)certain provider data 504 (e.g., the data-provider data table 400) withthe application 506.

At operation 606, the data platform 102 installs (in association withthe share 520) an application instance 556 of the application 506 in thedata-consumer account 552 of the data platform 102. The applicationinstance 556 includes APIs 558 that correspond to the APIs 508, and thatalso correspond to the (non-visible) underlying code blocks 560, whichthemselves correspond to the underlying code blocks 510.

At operation 608, the data platform 102 shares (at the share 562)certain consumer data 554 (e.g., the data-consumer data table 450) withthe application instance 556.

At operation 610, the data platform 102 invokes one or more of the APIs558 of the application instance 556 of the application 506.

At operation 612, the data platform 102 saves the output 570 of the APIs558 locally within the data-consumer account 552.

In an example embodiment, an API 558 may provide to the data-consumeraccount 552 a conversion rate that reflects the fraction of customersthat viewed a given advertisement via the streaming-video serviceassociated with the data-provider account 502—that actually went aheadand bought the advertised product (or service, etc.). With access toboth the data-provider data table 400 and the data-consumer data table450, the application instance 556 can compute a conversion rate on aproduct-by-product basis.

In the example data, it can be seen that advertisement 01 (correspondingto product 01) was viewed by the customers having the email addressesthat start with ‘name02’ and ‘name03.’ it can further be seen that the‘name02’ customer did not buy product 01, though the ‘name03’ customerdid. A conversion rate of 0.5 (1 out of 2, 50%, etc.) may be locallyreturned within the data-consumer account 552 for product 01.

For product 02, it can be seen that all four customers that areexplicitly listed in the data-provider data table 400 viewedadvertisement 02. These four customers have email addresses startingwith ‘name01,’ ‘name02,’ ‘name03,’ and ‘name04’ respectively. It canfurther be seen that the ‘name01’ customer, the ‘name02’ customer, andthe ‘name04’ customer bought product 02, whereas the ‘name03’ customerdid not. A conversion rate of 0.75 (3 out of 4, 75%, etc.) may bereturned within the data-consumer account 552 for product 02.

The above example shows that some APIs may provide results that are acertain count, average, fraction, percentage, and/or the like that arecomputed using data from both the provider and the consumer. Theseoperations thus anonymize the data by outputting only an aggregate(e.g., numerical) answer without exposing the underlying data from whichthat answer was computed.

In other cases, a relation (e.g., a table) may be returned locallywithin the data-consumer account 552. Depending on the functionality ofthe corresponding API, this relation may only be a subset of theconsumer data that was shared by the data-consumer account 552 with theapplication instance 556.

In some embodiments, an API may apply a differential privacy noiseparameter to return aggregate results that satisfy a specified epsilonvalue (i.e., privacy budget). Among other techniques, a given API mayinject a specific amount of Laplace noise into the aggregate results,although other techniques exist.

Various different embodiments provide advantages over priorimplementations. Some such advantages are described below. This list ofadvantages is intended to be illustrative and not limiting. Otheradvantages may occur to those of skill in the art having the benefit ofthe present disclosure.

Embodiments of the present disclosure give data providers flexibility indefining how they want their data to be accessed. For example, a dataprovider can create stored procedures and user-defined functions toenforce restrictions, One example context in which this may apply is inmachine learning. In that context, the contents of a model canpotentially reveal sensitive information about individuals, or revealproprietary information about hyperparameters and other detailsregarding how a given model was trained. To limit such exposure, a dataprovider may wish to allow consumers to access the provider'smachine-learning model only in certain ways. For example, a provider mayallow a consumer to generate predictions, and optionally to contributetraining data, without allowing the consumer to directly inspect themodel. In such an embodiment, the provider creates APIs to access themodel (i.e., “predict” API and optionally “train” API), and the consumercan only interact with the model via these APIs. Additionally, theprovider can limit the number of predictions that the consumer canperform. A relevant use case is fraud detection in financial services:Banks wish to collaborate to build models to detect fraudulentconsumers, but may be prevented by regulation and business interestsfrom sharing raw consumer data with one another. Homomorphic encryptionmay be used in some embodiments related to machine-learning models.

At least one embodiment supports limiting the extent of a consumer'saccess to data. For example, an embodiment can keep state that trackshow many queries a consumer has issued, or the aggregate amount of datathe consumer has retrieved, or the privacy loss metric in differentialprivacy, as examples. Based on these metrics, the data platform canrestrict the consumer's access if too much data has been accessed, intotal or over a discrete time period (rate-limiting), Other examples arepossible as well. Moreover, in embodiments that utilize homomorphicencryption, limits can be placed on the number of calculations that maybe performed, in order to keep the accumulating noise in thehomomorphically encrypted data at a level at which the data consumer'ssecret key will still be operable to decrypt the results.

At least one embodiment supports global collaboration across clouds andgeographical regions. When an authorized consumer wants to access datathat a provider has shared, the data platform may automaticallyreplicate the data to the region where it is needed, so that theconsumer can install it as an application instance.

At least one embodiment supports collaboration across X parties, where Xcan be 2 or greater. In an X-party scenario, one party acts as theconsumer, combining data from the X-1 other parties and optionally datafrom itself.

As mentioned above, in at least one embodiment, usage of installedapplication instances of applications are auditable. As a first example,a data platform can provide a generic audit mechanism in the form of alog of API calls. As a second example, a data platform can provide alogging facility that providers' code can invoke to loguse-case-specific context, e.g., how much of the consumer's privacybudget is consumed by the current call. Other audit mechanisms and/orauditable events may be implemented in various different embodiments.

At least one embodiment is integrated with the data platform's SQL queryprocessing platform, so consumers can directly use the results fromclean rooms as inputs to arbitrary computations that the consumer wantsto perform.

In some embodiments, data providers can create user interfaces as partof their applications. For example, a provider might wish to shareaggregate data about individuals without revealing individual records.The provider can give consumers access to data in the form of adashboard. The dashboard might include graphs and charts, and provideconsumers with ways to customize the dashboard. For example, in aninteractive dashboard, the consumer may be able to specify filters,grouping conditions/breakdowns, time ranges, and so forth, to customizethe aggregate results that are displayed. In an embodiment, theunderlying data for the dashboard comes from APIs of platform functionsas described herein. The APIs may include parameters that the dataconsumer can set, through the dashboard, to customize the aggregatequantities that are returned. The APIs may also restrict how the dataconsumer can customize the dashboard. For example, the provider's codemay prevent the consumer from setting filter conditions that coulduniquely identify an individual.

Various TEE embodiments are discussed below. It is noted that thevarious possibilities and permutations described above in connectionwith common-platform embodiments could also be realized as TEEembodiments, other than any cases in which a given embodiment ispossible in a common-platform scenario but not in a TEE scenario.

FIG. 7 depicts an example defined-access data-clean-room scenario 700,in accordance with at least one embodiment. Depicted in FIG. 7 arerepresentations of (i) a data-provider platform 702 corresponding withthe above-described streaming-video platform and (ii) a data-consumerplatform 752 corresponding with the above-described advertiser. Thedata-provider platform 702 includes provider data 704 and an application706. The provider data 704 may include the data-provider data table 400of FIG. 4 . Furthermore, a share 712 is depicted to represent that atleast some of the provider data 704 is shared with the application 706.In this example, the shared data is the data-provider data table 400.

Furthermore, the application 706 includes one or more APIs 708 thatcorrespond with one or more respective underlying code blocks 710. TheseAPIs 708 and associated underlying code blocks 710 could provide any ofthe operations described above, including queries, query operations(e.g., joins), user-defined functions, stored procedures, access to oneor more secure views, generation of one or more user-interface elements,and/or the like. In at least one embodiment, the underlying code blocks710 contain the source code and/or executable code that actuallyperforms the operations that are accessible via the APIs 708.

A share 720 depicts that the data-provider platform 702 is sharing theapplication 706 with a TEE 772. In at least one embodiment, thisinvolves installing an application instance 756 of the application 706in the TEE 772. As can be seen in FIG. 7 , the application instance 756includes one or more APIs 758 that correspond to the one or more APIs708 of the application 706. The APIs 758 respectively provide access toone or more underlying code blocks 760, which correspond to the one ormore underlying code blocks 710 in the application 706. Whereas theunderlying code blocks 710 (e.g., the underlying source code and/orexecutable code) are visible on the data-provider platform 702, theunderlying code blocks 760 are not visible in the TEE 772 for thisreason, the underlying code blocks 760 are depicted using dashedoutlines in FIG. 7 .

It can further be seen that a data-consumer platform 752 containsconsumer data 754 which, in this example, includes the above-describeddata-consumer data table 450 of FIG. 4 . The share 762 that is depictedin FIG. 7 represents that the data-consumer platform 752 is sharing atleast some of the consumer data 754 with the application instance 756.It is noted with respect to both the provider data 704 and the consumerdata 754 that their depiction as being respectively on the data-providerplatform 702 and the data-consumer platform 752 are illustrative only,and do not necessarily reflect an actual storage location.

When the data-consumer platform 752 uses one or more of the APIs 758 ofthe application instance 556 in the TEE 772, any output of theseoperations is depicted as being stored back in the consumer data 754 onthe data-consumer platform 752. The security of the consumer data 754 isprotected in at least two ways: it is processed in the TEE 772, and theresulting output 770 is stored back to the data-consumer platform 752.In at least one embodiment, the shared provider data 704, the sharedconsumer data 754, the operations performed pursuant to the APIs 758,and the output 770 are all protected by homomorphic encryption, asdescribed herein.

FIG. 8 shows a flow diagram of a method 800 for providing defined accessin the context of a data clean room, in accordance with at least oneembodiment. The example method 800 is described by way of example asbeing performed in the context of FIG. 7 , though this is by way ofexample and not limitation. Furthermore, the method 800 could beperformed by any one or more computing devices that are suitablyprogrammed to perform the described functions.

At operation 802, the application 706 is created on the data-providerplatform 702. The application 706 includes one or more APIs 708corresponding to one or more underlying code blocks 710.

At operation 804, the data-provider platform 702 shares (at the share712) certain provider data 704 (e.g., the data-provider data table 400)with the application 706.

At operation 806, the data-provider platform 702 installs (inassociation with the share 720) an application instance 756 of theapplication 706 in the TEE 772. The application instance 756 includesAPIs 758 that correspond to the APIs 708, and that also correspond tothe (non-visible) underlying code blocks 760, which themselvescorrespond to the underlying code blocks 710.

At operation 808, the data-consumer platform 752 shares (at the share762) certain consumer data 754 (e.g., the data-consumer data table 450)with the application instance 756 on the TEE 772.

At operation 810, the data-consumer platform 752 invokes one or more ofthe APIs 758 of the application instance 756 of the application 706 onthe TEE 772.

At operation 812, the data-consumer platform 752 saves the output 770 ofthe APIs 758 locally on the data-consumer platform 752.

Below is a description of FIG. 9 and FIG. 10 , which relate tocryptography embodiments. These are provided by way of example and notlimitation. In the below description of FIG. 9 and FIG. 10 , the examplecryptographic mechanism that is utilized is FHE.

FIG. 9 depicts an example defined-access data-clean-room scenario 900,in accordance with at least one embodiment. Depicted in FIG. 9 arerepresentations of (i) a data-provider platform 902 corresponding withthe above-described streaming-video platform and (ii) a data-consumerplatform 952 corresponding with the above-described advertiser. Thedata-provider platform 902 includes provider data 904 and an application906. The provider data 904 may include the data-provider data table 400of FIG. 4 . Furthermore, a share 912 is depicted to represent that atleast some of the provider data 904 is shared with the application 906,In this example, the shared data is the data-provider data table 400.Moreover, as indicated by the lock icon on the share 912, in thisembodiment, the provider data that is shared by the share 912 ishomomorphically encrypted with a public key provided to the dataprovider by the data consumer.

Furthermore, the application 906 includes one or more APIs 908 thatcorrespond with one or more respective underlying code blocks 910 thatimplement cryptographic processing, in this case using FHE. These APIs908 and associated underlying code blocks 910 could provide any of theoperations described above, including queries, query operations (e.g.,joins), user-defined functions, stored procedures, access to one or moresecure views, generation of one or more user-interface elements, and/orthe like. In at least one embodiment, the underlying code blocks 910contain the source code and/or executable code that actually performsthe operations that are accessible via the APIs 908. The lock icon onthe underlying code blocks 910 indicates that the operations performedwill be on homomorphically encrypted data, as described herein.

A share 920 depicts that the data-provider platform 902 is sharing theapplication 906 with the data-consumer platform 952. In at least oneembodiment, the share 920 permits the installation in the data-consumerplatform 952 of an application instance 956 of the application 906. Theshare 920 is depicted with a lock icon to indicate that, like theapplication 906, the application instance 956 also implements FHE.

As can be seen in FIG. 9 , the application instance 956 includes one ormore APIs 958 that correspond to the one or more APIs 908 of theapplication 906. The APIs 958 respectively provide access to one or moreunderlying code blocks 960, which correspond to the one or moreunderlying code blocks 910 in the application 906. Like the underlyingcode blocks 910 to which they correspond, the underlying code blocks 960are also depicted with a lock icon to indicate that they operate onhomomorphically encrypted data. Whereas the underlying code blocks 910(e.g., the underlying source code and/or executable code) are visible tothe data-provider platform 902, the underlying code blocks 960 are notvisible to the data-consumer platform 952 for this reason, theunderlying code blocks 960 are depicted using dashed outlines in FIG. 6.

It can further be seen that the data-consumer platform 952 containsconsumer data 954 which, in this example, includes the above-describeddata-consumer data table 450 of FIG. 4 , The share 962 that is depictedin FIG. 9 represents that the data-consumer platform 952 is sharing atleast some of the consumer data 954 with the application instance 956.Moreover, the lock icon on the share 962 indicates that the data sharedby the share 962 is homomorphically encrypted, in this example with theaforementioned public key generated by (or for) the data consumer. It isnoted with respect to both the provider data 904 and the consumer data954 that their depiction as being respectively within the data-providerplatform 902 and the data-consumer platform 952 are illustrative only,and do not necessarily reflect an actual storage location.

When the data-consumer platform 952 uses one or more of the APIs 958 ofthe application instance 956, FHE processing is conducted such that theinputs to the APIs 958 are encrypted, as is the output 970 in at leastone embodiment. The output 970 of these operations is depicted as beingstored in the consumer data 954 of the data-consumer platform 952. Thelock icon on the output 970 indicates that, in at least someembodiments, the output 970 is encrypted with, e.g., the public key ofthe data consumer. The data consumer may use the corresponding secretkey to decrypt the output 970 for storage, substantive use, gaininginsight, and/or the like.

Moreover, the data-consumer platform 952 may re-encrypt those decryptionresults for storage at rest, for transmission to another entity, etc. Inat least some embodiments, the security of the consumer data 954 isprotected in at least three ways: it never leaves the data-consumerplatform 952, the resulting output 970 is locally stored in thedata-consumer platform 952, and homomorphic encryption as describedherein masks, in at least one embodiment, the substantive contents ofthe shared portion of the provider data 904, the shared portion of theconsumer data 954, the operations of the underlying code blocks 960 atthe behest of the APIs 958, and the output 970.

FIG. 10 shows a flow diagram of a third method for providing definedaccess in the context of a data clean room, in accordance with at leastone embodiment. In particular, FIG. 10 depicts an example method 1000that implements FHE as described herein.

At operation 1002, the application 906 is created on the data-providerplatform 902. The application 906 includes one or more APIs 908corresponding to one or more underlying code blocks 910, which areconfigured to be able to operate on homomorphically encrypted data, asdescribed herein.

At operation 1004, the data-provider platform 902 shares (at the share912) certain provider data 904 (e.g., the data-provider data table 400)with the application 906. In at least some embodiments, the sharedportion of the provider data 904 is homomorphically encrypted with,e.g., a public key provided by the data consumer.

At operation 1006, the data-provider platform 902 installs (inassociation with the share 920) an application instance 956 of theapplication 906 in the data-consumer platform 952. The applicationinstance 956 includes APIs 958 that correspond to the APIs 908, and thatalso correspond to the (non-visible) underlying code blocks 960, whichthemselves correspond to the underlying code blocks 910, and implementFHE processing as described herein.

At operation 1008, the data-consumer platform 952 shares (at the share962) certain consumer data 954 (e.g., the data-consumer data table 450)with the application instance 956. The shared portion of the consumerdata 954 may also be homomorphically encrypted, in an example with theaforementioned public key of the data consumer.

At operation 1010, the data-consumer platform 952 invokes one or more ofthe APIs 958 of the application instance 956 of the application 906,resulting in one or more of the underlying code blocks 960 operating onhomomorphically encrypted data.

At operation 1012, the data-consumer platform 952 saves the output 970of the APIs 958 locally within the data-consumer platform 952. Asdescribed above, the output 970 may also be homomorphically encryptedwith the public key of the data consumer, where only the data consumerpossesses the corresponding secret key needed to decrypt the output 970.

FIG. 11 illustrates a diagrammatic representation of a machine 1100 inthe form of a computer system within which a set of instructions may beexecuted for causing the machine 1100 to perform any one or more of themethodologies discussed herein, according to an example embodiment.Specifically, FIG. 11 shows a diagrammatic representation of the machine1100 in the example form of a computer system, within which instructions1116 (e.g., software, a program, an application, an applet, an app, orother executable code), for causing the machine 1100 to perform any oneor more of the methodologies discussed herein, may be executed. Forexample, the instructions 1116 may cause the machine 1100 to execute anyone or more operations of any one or more of the methods describedherein, by one or more processors. As another example, the instructions1116 may cause the machine 1100 to implement portions of the data flowsdescribed herein, in this way, the instructions 1116 transform ageneral, non-programmed machine into a particular machine 1100 (e.g.,the client device 114 of FIG. 1 , the compute service manager 108 ofFIG. 1 , the execution platform 110 of FIG. 1 ) that is speciallyconfigured to carry out any one of the described and illustratedfunctions in the manner described herein.

In alternative embodiments, the machine 1100 operates as a standalonedevice or may be coupled (e.g., networked) to other machines. In anetworked deployment, the machine 1100 may operate in the capacity of aserver machine or a client machine in a server-client networkenvironment, or as a peer machine in a peer-to-peer (or distributed)network environment. The machine 1100 may comprise, but not be limitedto, a server computer, a client computer, a personal computer (PC), atablet computer, a laptop computer, a netbook, a smart phone, a mobiledevice, a network router, a network switch, a network bridge, or anymachine capable of executing the instructions 1116, sequentially orotherwise, that specify actions to be taken by the machine 1100.Further, while only a single machine 1100 is illustrated, the term“machine” shall also be taken to include a collection of machines 1100that individually or jointly execute the instructions 1116 to performany one or more of the methodologies discussed herein.

The machine 1100 includes processors 1110, memory 1130, and input/output(I/O) components 1150 configured to communicate with each other such asvia a bus 1102. In an example embodiment, the processors 1110 (e.g., acentral processing unit (CPU), a reduced instruction set computing(RISC) processor, a complex instruction set computing (CISC) processor,a graphics processing unit (GPU), a digital signal processor (DSP), anapplication-specific integrated circuit (ASIC), a radio-frequencyintegrated circuit (RFIC), another processor, or any suitablecombination thereof) may include, for example, a processor 1112 and aprocessor 1114 that may execute the instructions 1116. The term“processor” is intended to include multi-core processors 1110 that maycomprise two or more independent processors (sometimes referred to as“cores”) that may execute instructions 1116 contemporaneously, AlthoughFIG. 11 shows multiple processors 1110, the machine 1100 may include asingle processor with a single core, a single processor with multiplecores (e.g., a multi-core processor), multiple processors with a singlecore, multiple processors with multiple cores, or any combinationthereof.

The memory 1130 may include a main memory 1132, a static memory 1134,and a storage unit 1131, all accessible to the processors 1110 such asvia the bus 1102. The main memory 1132, the static memory 1134, and thestorage unit 1131 comprise a machine storage medium 1138 that may storethe instructions 1116 embodying any one or more of the methodologies orfunctions described herein. The instructions 1116 may also reside,completely or partially, within the main memory 1132, within the staticmemory 1134, within the storage unit 1131, within at least one of theprocessors 1110 (e.g., within the processor's cache memory), or anysuitable combination thereof, during execution thereof by the machine1100.

The I/O components 1150 include components to receive input, provideoutput, produce output, transmit information, exchange information,capture measurements, and so on. The specific I/O components 1150 thatare included in a particular machine 1100 will depend on the type ofmachine. For example, portable machines, such as mobile phones, willlikely include a touch input device or other such input mechanisms,while a headless server machine will likely not include such a touchinput device. It will be appreciated that the I/O components 1150 mayinclude many other components that are not shown in FIG. 11 . The I/Ocomponents 1150 are grouped according to functionality merely forsimplifying the following discussion and the grouping is in no waylimiting. In various example embodiments, the I/O components 1150 mayinclude output components 1152 and input components 1154.

The output components 1152 may include visual components (e.g., adisplay such as a plasma display panel (PDP), a light emitting diode(LED) display, a liquid crystal display (LCD), a projector, or a cathoderay tube (CRT)), acoustic components (e.g., speakers), other signalgenerators, and so forth. The input components 1154 may includealphanumeric input components (e.g., a keyboard, a touch screenconfigured to receive alphanumeric input, a photo-optical keyboard, orother alphanumeric input components), point-based input components(e.g., a mouse, a touchpad, a trackball, a joystick, a motion sensor, oranother pointing instrument), tactile input components (e.g., a physicalbutton, a touch screen that provides location and/or force of touches ortouch gestures, or other tactile input components), audio inputcomponents (e.g., a microphone), and the like.

Communication may be implemented using a wide variety of technologies.The I/O components 1150 may include communication components 1164operable to couple the machine 1100 to a network 1181 via a coupling1183 or to devices 1180 via a coupling 1182, For example, thecommunication components 1164 may include a network interface componentor another suitable device to interface with the network 1181. Infurther examples, the communication components 1164 may include wiredcommunication components, wireless communication components, cellularcommunication components, and other communication components to providecommunication via other modalities. The devices 1180 may be anothermachine or any of a wide variety of peripheral devices (e.g., aperipheral device coupled via a universal serial bus (USB)). Forexample, as noted above, the machine 1100 may correspond to any one ofthe client device 114, the compute service manager 108, and theexecution platform 110, and may include any other of these systems anddevices.

The various memories (e.g., 1130, 1132, 1134, and/or memory of theprocessor(s) 1110 and/or the storage unit 1136) may store one or moresets of instructions 1116 and data structures (e.g., software),embodying or utilized by any one or more of the methodologies orfunctions described herein. These instructions 1116, when executed bythe processor(s) 1110, cause various operations to implement thedisclosed embodiments.

As used herein, the terms “machine-storage medium,” “device-storagemedium,” and “computer-storage medium” mean the same thing and may beused interchangeably in this disclosure. The terms refer to a single ormultiple storage devices and/or media (e.g., a centralized ordistributed database, and/or associated caches and servers) that storeexecutable instructions and/or data. The terms shall accordingly betaken to include, but not be limited to; solid-state memories; andoptical and magnetic media, including memory internal or external toprocessors. Specific examples of machine-storage media, computer-storagemedia; and/or device-storage media include non-volatile memory,including by way of example semiconductor memory devices, (e.g.,erasable programmable read-only memory (EPROM), electrically erasableprogrammable read-only memory (EEPROM), field-programmable gate arrays(FPGAs), and flash memory devices); magnetic disks such as internal harddisks and removable disks; magneto-optical disks; and CD-ROM and DVD-ROMdisks. The terms “machine-storage media,” “computer-storage media,” and“device-storage media” specifically exclude carrier waves, modulateddata signals, and other such media, at least some of which are coveredunder the term “signal medium” discussed below.

In various example embodiments, one or more portions of the network 1181may be an ad hoc network, an intranet, an extranet, a virtual privatenetwork (VPN), a local-area network (LAN), a wireless LAN (WLAN), awide-area network (WAN), a wireless WAN (WWAN), a metropolitan-areanetwork (MAN), the Internet, a portion of the Internet, a portion of thepublic switched telephone network (PSTN), a plain old telephone service(POTS) network, a cellular telephone network, a wireless network, aWi-Fi® network, another type of network, or a combination of two or moresuch networks. For example, the network 1181 or a portion of the network1181 may include a wireless or cellular network, and the coupling 1182may be a Code Division Multiple Access (CDMA) connection, a GlobalSystem for Mobile communications (GSM) connection, or another type ofcellular or wireless coupling. In this example, the coupling 1182 mayimplement any of a variety of types of data transfer technology, such asSingle Carrier Radio Transmission Technology (1×RTT), Evolution-DataOptimized (EVDO) technology, General Packet Radio Service (GPRS)technology, Enhanced Data rates for GSM Evolution (EDGE) technology,third Generation Partnership Project (3GPP) including 3G, fourthgeneration wireless (4G) networks, Universal Mobile TelecommunicationsSystem (UNITS), High-Speed Packet Access (HSPA), WorldwideInteroperability for Microwave Access (WiMAX), Long Term Evolution (LTE)standard, others defined by various standard-setting organizations,other long-range protocols, or other data transfer technology.

The instructions 1116 may be transmitted or received over the network1181 using a transmission medium via a network interface device (e.g., anetwork interface component included in the communication components1164), and utilizing any one of a number of well-known transferprotocols (e.g., hypertext transfer protocol (HTTP)). Similarly, theinstructions 1116 may be transmitted or received using a transmissionmedium via the coupling 1182 (e.g., a peer-to-peer coupling) to thedevices 1180. The terms “transmission medium” and “signal medium” meanthe same thing and may be used interchangeably in this disclosure. Theterms “transmission medium” and “signal medium” shall be taken toinclude any intangible medium that is capable of storing, encoding, orcarrying the instructions 1116 for execution by the machine 1100, andinclude digital or analog communications signals or other intangiblemedia to facilitate communication of such software. Hence, the terms“transmission medium” and “signal medium” shall be taken to include anyform of modulated data signal, carrier wave, and so forth. The term“modulated data signal” means a signal that has one or more of itscharacteristics set or changed in such a manner as to encode informationin the signal.

The terms “machine-readable medium,” “computer-readable medium,” and“device-readable medium” mean the same thing and may be usedinterchangeably in this disclosure. The terms are defined to includeboth machine-storage media and transmission media. Thus, the termsinclude both storage devices/media and carrier waves/modulated datasignals.

In view of the disclosure above, a listing of various examples ofembodiments is set forth below. It should be noted that one or morefeatures of an example, taken in isolation or combination, should beconsidered to be within the disclosure of this application.

Example 1 is a method performed by executing instructions on at leastone hardware processor, the method including: creating an application ona data-provider platform, the application including one or moreapplication programming interfaces (APIs) corresponding to one or moreunderlying code blocks; sharing provider data with the application onthe data-provider platform; installing, in a trusted executionenvironment (TEE), an application instance of the application, theapplication instance including one or more APIs corresponding to the oneor more APIs in the application on the data-provider platform; sharingconsumer data with the application instance from a data-consumerplatform; invoking one or more of the APIs of the application instanceto execute respective associated underlying code blocks on the TEE, therespective associated underlying code blocks not being visible on theTEE; and saving output of the one or more respective associatedunderlying code blocks to the data-consumer platform.

Example 2 is the method of Example 1, where the application instance is,by default, not authorized to exfiltrate consumer data from thedata-consumer platform.

Example 3 is the method of Example 1 or Example 2, where the respectiveassociated underlying code blocks not being visible on the TEE includesa source code of the respective associated underlying code blocks notbeing visible on the TEE.

Example 4 is the method of any of the Examples 1-3, where the savedoutput includes aggregated output data.

Example 5 is the method of Example 4, where the saved output does notinclude any of the shared provider data.

Example 6 is the method of any of the Examples 1-5, where the savedoutput includes a relation.

Example 7 is the method of Example 6, where the relation includes only asubset of the consumer data that was shared with the applicationinstance.

Example 8 is a computer system including: at least one hardwareprocessor; and one or more non-transitory computer readable storagemedia containing instructions that, when executed by the at least onehardware processor, cause the computer system to perform operationsincluding: creating an application on a data-provider platform, theapplication including one or more application programming interfaces(APIs) corresponding to one or more underlying code blocks; sharingprovider data with the application on the data-provider platform;installing, in a trusted execution environment (TEE), an applicationinstance of the application, the application instance including one ormore APIs corresponding to the one or more APIs in the application onthe data-provider platform; sharing consumer data with the applicationinstance from a data-consumer platform; invoking one or more of the APIsof the application instance to execute respective associated underlyingcode blocks on the TEE, the respective associated underlying code blocksnot being visible on the TEE; and saving output of the one or morerespective associated underlying code blocks to the data-consumerplatform.

Example 9 is the computer system of Example 8, where the applicationinstance is, by default, not authorized to exfiltrate consumer data fromthe data-consumer platform.

Example 10 is the computer system of Example 8 or Example 9, where therespective associated underlying code blocks not being visible on theTEE includes a source code of the respective associated underlying codeblocks not being visible on the TEE.

Example 11 is the computer system of any of the Examples 8-10, where thesaved output includes aggregated output data.

Example 12 is the computer system of Example 11, where the saved outputdoes not include any of the shared provider data.

Example 13 is the computer system of any of the Examples 8-12, where thesaved output includes a relation.

Example 14 is the computer system of Example 13, where the relationincludes only a subset of the consumer data that was shared with theapplication instance.

Example 15 is one or more non-transitory computer readable storage mediacontaining instructions that, when executed by at least one hardwareprocessor of a computer system, cause the computer system to performoperations including: creating an application on a data-providerplatform, the application including one or more application programminginterfaces (APIs) corresponding to one or more underlying code blocks;sharing provider data with the application on the data-providerplatform; installing, in a trusted execution environment (TEE), anapplication instance of the application, the application instanceincluding one or more APIs corresponding to the one or more APIs in theapplication on the data-provider platform; sharing consumer data withthe application instance from a data-consumer platform; invoking one ormore of the APIs of the application instance to execute respectiveassociated underlying code blocks on the TEE, the respective associatedunderlying code blocks not being visible on the TEE; and saving outputof the one or more respective associated underlying code blocks to thedata-consumer platform.

Example 16 is the one or more non-transitory computer readable storagemedia of Example 15, where the application instance is, by default, notauthorized to exfiltrate consumer data from the data-consumer platform.

Example 17 is the one or more non-transitory computer readable storagemedia of Example 15 or Example 16, where the respective associatedunderlying code blocks not being visible on the TEE includes a sourcecode of the respective associated underlying code blocks not beingvisible on the TEE.

Example 18 is the one or more non-transitory computer readable storagemedia of any of the Examples 15-18, where the saved output includesaggregated output data.

Example 19 is the one or more non-transitory computer readable storagemedia of Example 18, where the saved output does not include any of theshared provider data.

Example 20 is the one or more non-transitory computer readable storagemedia of any of the Examples 15-19, where the saved output includes arelation.

Example 21 is the one or more non-transitory computer readable storagemedia of Example 20, where the relation includes only a subset of theconsumer data that was shared with the application instance.

In at least one embodiment, the application is already in thedata-provider account, and need not be created as part of an embodiment.

The various operations of example methods described herein may beperformed, at least partially, by one or more processors that aretemporarily configured (e.g., by software) or permanently configured toperform the relevant operations. Similarly, the methods described hereinmay be at least partially processor-implemented. For example, at leastsome of the operations of the methods described herein may be performedby one or more processors. The performance of certain of the operationsmay be distributed among the one or more processors, not only residingwithin a single machine, but also deployed across a number of machines.In some embodiments, the processor or processors may be located in asingle location (e.g., within a home environment, an office environment,or a server farm), while in other embodiments the processors may bedistributed across a number of locations.

Although the embodiments of the present disclosure have been describedwith reference to specific example embodiments, it will be evident thatvarious modifications and changes may be made to these embodimentswithout departing from the broader scope of the inventive subjectmatter. Accordingly, the specification and drawings are to be regardedin an illustrative rather than a restrictive sense. The accompanyingdrawings that form a part hereof show, by way of illustration, and notof limitation, specific embodiments in which the subject matter may bepracticed. The embodiments illustrated are described in sufficientdetail to enable those skilled in the art to practice the teachingsdisclosed herein. Other embodiments may be used and derived therefrom,such that structural and logical substitutions and changes may be madewithout departing from the scope of this disclosure. This detaileddescription, therefore, is not to be taken in a limiting sense, and thescope of various embodiments is defined only by the appended claims,along with the full range of equivalents to which such claims areentitled.

Such embodiments of the inventive subject matter may be referred toherein, individually and/or collectively, by the term “invention” merelyfor convenience and without intending to voluntarily limit the scope ofthis application to any single invention or inventive concept if morethan one is in fact disclosed. Thus, although specific embodiments havebeen illustrated and described herein, it should be appreciated that anyarrangement calculated to achieve the same purpose may be substitutedfor the specific embodiments shown. This disclosure is intended to coverany and all adaptations or variations of various embodiments.Combinations of the above embodiments, and other embodiments notspecifically described herein, will be apparent to those of skill in theart, upon reviewing the above description.

In this document, the terms “a” or “an” are used, as is common in patentdocuments, to include one or more than one, independent of any otherinstances or usages of “at least one” or “one or more.” In thisdocument, the term “or” is used to refer to a nonexclusive or, such that“A or B” includes “A but not B,” “B but not A,” and “A and B,” unlessotherwise indicated. In the appended claims, the terms “including” and“in which” are used as the plain-English equivalents of the respectiveterms “comprising” and “wherein.” Also, in the following claims, theterms “including” and “comprising” are open-ended; that is, a system,device, article, or process that includes elements in addition to thoselisted after such a term in a claim is still deemed to fall within thescope of that claim.

What is claimed is:
 1. A method performed by executing instructions onat least one hardware processor, the method comprising: creating anapplication in a data-provider account of a data platform, theapplication comprising one or more application programming interfaces(APIs) corresponding to one or more underlying code blocks; sharinghomomorphically encrypted provider data with the application in thedata-provider account; installing, in a data-consumer account of thedata platform, an application instance of the application, theapplication instance comprising one or more APIs corresponding to theone or more APIs in the application in the data-provider account;sharing homomorphically encrypted consumer data with the applicationinstance in the data-consumer account; invoking one or more of the APIsof the application instance to execute respective associated underlyingcode blocks, the respective associated underlying code blocks not beingvisible to the data-consumer account, the respective associatedunderlying code blocks not being visible to the data-consumer accountcomprising a source code of the respective associated underlying codeblocks not being visible to the data-consumer account, the one or moreexecuted underlying code blocks operating on the shared homomorphicallyencrypted provider data and the shared homomorphically encryptedconsumer data; and saving homomorphically encrypted output of the one ormore respective associated underlying code blocks locally within thedata-consumer account, the shared homomorphically encrypted providerdata, the shared homomorphically encrypted consumer data, and thehomomorphically encrypted output each being homomorphically encryptedusing a public key generated by the data-consumer account.
 2. The methodof claim Hai, further comprising the data-consumer account sharing thepublic key with the data-provider account.
 3. The method of claim 1,wherein the application instance is, by default, not authorized toexfiltrate consumer data from the data-consumer account.
 4. The methodof claim 1, wherein the saved homomorphically encrypted output comprisesaggregated output data.
 5. The method of claim 4, wherein the savedhomomorphically encrypted output does not include any of the sharedprovider data.
 6. The method of claim 1, wherein the savedhomomorphically encrypted output comprises a relation.
 7. The method ofclaim 6, wherein the relation includes only a subset of the sharedhomomorphically encrypted consumer data.
 8. The method of claim 1,further comprising locally decrypting the homomorphically encryptedoutput for storage in the data-consumer account.
 9. A data platformcomprising: at least one hardware processor; and one or morenon-transitory computer readable storage media containing instructionsthat, when executed by the at least one hardware processor, cause thedata platform to perform operations comprising: creating an applicationin a data-provider account of a data platform, the applicationcomprising one or more application programming interfaces (APIs)corresponding to one or more underlying code blocks; sharinghomomorphically encrypted provider data with the application in thedata-provider account; installing, in a data-consumer account of thedata platform, an application instance of the application, theapplication instance comprising one or more APIs corresponding to theone or more APIs in the application in the data-provider account;sharing homomorphically encrypted consumer data with the applicationinstance in the data-consumer account; invoking one or more of the APIsof the application instance to execute respective associated underlyingcode blocks, the respective associated underlying code blocks not beingvisible to the data-consumer account, the respective associatedunderlying code blocks not being visible to the data-consumer accountcomprising a source code of the respective associated underlying codeblocks not being visible to the data-consumer account, the one or moreexecuted underlying code blocks operating on the shared homomorphicallyencrypted provider data and the shared homomorphically encryptedconsumer data; and saving homomorphically encrypted output of the one ormore respective associated underlying code blocks locally within thedata-consumer account, the shared homomorphically encrypted providerdata, the shared homomorphically encrypted consumer data, and thehomomorphically encrypted output each being homomorphically encryptedusing a public key generated by the data-consumer account.
 10. The dataplatform of claim 9, the operations further comprising the data-consumeraccount sharing the public key with the data-provider account.
 11. Thedata platform of claim 9, wherein the application instance is, bydefault, not authorized to exfiltrate consumer data from thedata-consumer account.
 12. The data platform of claim 9, wherein thesaved homomorphically encrypted output comprises aggregated output data.13. The data platform of claim 12, wherein the saved homomorphicallyencrypted output does not include any of the shared provider data. 14.The data platform of claim 9, wherein the saved homomorphicallyencrypted output comprises a relation.
 15. The data platform of claim14, wherein the relation includes only a subset of the sharedhomomorphically encrypted consumer data.
 16. The data platform of claim9, the operations further comprising locally decrypting thehomomorphically encrypted output for storage in the data-consumeraccount.
 17. One or more non-transitory computer readable storage mediacontaining instructions that, when executed by at least one hardwareprocessor of a computer system, cause the computer system to performoperations comprising: creating an application in a data-provideraccount of a data platform, the application comprising one or moreapplication programming interfaces (APIs) corresponding to one or moreunderlying code blocks; sharing homomorphically encrypted provider datawith the application in the data-provider account; installing, in adata-consumer account of the data platform, an application instance ofthe application, the application instance comprising one or more APIscorresponding to the one or more APIs in the application in thedata-provider account; sharing homomorphically encrypted consumer datawith the application instance in the data-consumer account; invoking oneor more of the APIs of the application instance to execute respectiveassociated underlying code blocks, the respective associated underlyingcode blocks not being visible to the data-consumer account, therespective associated underlying code blocks not being visible to thedata-consumer account comprising a source code of the respectiveassociated underlying code blocks not being visible to the data-consumeraccount, the one or more executed underlying code blocks operating onthe shared homomorphically encrypted provider data and the sharedhomomorphically encrypted consumer data; and saving homomorphicallyencrypted output of the one or more respective associated underlyingcode blocks locally within the data-consumer account, the sharedhomomorphically encrypted provider data, the shared homomorphicallyencrypted consumer data, and the homomorphically encrypted output eachbeing homomorphically encrypted using a public key generated by thedata-consumer account.
 18. The one or more non-transitory computerreadable storage media of claim 17, the operations further comprisingthe data-consumer account sharing the public key with the data-provideraccount.
 19. The one or more non-transitory computer readable storagemedia of claim 17, wherein the application instance is, by default, notauthorized to exfiltrate consumer data from the data-consumer account.20. The one or more non-transitory computer readable storage media ofclaim 17, wherein the saved homomorphically encrypted output comprisesaggregated output data.
 21. The one or more non-transitory computerreadable storage media of claim 20, wherein the saved homomorphicallyencrypted output does not include any of the shared provider data. 22.The one or more non-transitory computer readable storage media of claim17, wherein the saved homomorphically encrypted output comprises arelation.
 23. The one or more non-transitory computer readable storagemedia of claim 22, wherein the relation includes only a subset of theshared homomorphically encrypted consumer data.
 24. The one or morenon-transitory computer readable storage media of claim 17, theoperations further comprising locally decrypting the homomorphicallyencrypted output for storage in the data-consumer account.